home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD Exchange
/
CD Exchange - Volume 1.iso
/
graphics
/
utils
/
hamlabplus_demo
/
documentation
/
cmd-ref.doc
next >
Wrap
Text File
|
1992-08-09
|
40KB
|
1,527 lines
HAMLAB PLUS 2.0.8
AREXX / CONFIG FILE COMMAND REFERENCE
(c) Copyright 1992 J. E. Hanway. All rights reserved.
IN THIS DOCUMENT:
BACKGROUND
AREXX SYNTAX
CONFIG FILE SYNTAX
COMMAND LIST
COMMAND DESCRIPTIONS
HAMLAB PLUS ATTRIBUTES
BACKGROUND
HAMLAB PLUS uses the standard AmigaDOS command syntax for both AREXX
commands and config file commands.
A good description of AmigaDOS command conventions can be found in
Chapter 8 of "Using the System Software," the AmigaOS Release 2 User's
manual.
All commands are valid in AREXX programs. A subset are also valid in
config files. Those are noted by one or more of the following special
symbols after the command name:
* means that the command is valid in a config file
S means the command will be included in a file generated by the
"Save Config" operation
A means the command will be included in a file generated by the
"Save All" operation
All commands and keywords are insensitive to upper/lower case.
String arguments should be enclosed in double quotes and may include
spaces and the following escape sequences:
\n new line
\r carriage return
\t horizontal tab
\a bell
\\ backslash
\nnn nnn is three octal digits representing the character
code
AREXX SYNTAX
In order to pass a command to HAMLAB PLUS from an AREXX program, it
must be distinguished from a built-in AREXX command, usually by
enclosing it in single quotes to make it a string. For example, to
display the message "Hello, world!" in an AREXX program, the actual
line in the program could look like:
'MESSAGE "Hello, world!"'
The external single quotes are interpreted by AREXX, and the internal
double quotes are processed by HAMLAB PLUS. Of course, it is probably
more typical to build complex commands using AREXX's string operators.
For example:
'MESSAGE' '"Current value of foo,bar is' foo||','||bar '"'
CONFIG FILE SYNTAX
Although config files share some of the same commands as AREXX
programs, they are NOT AREXX programs. Although this means that you
can't use AREXX program statements and variables in your config files,
it does mean that config files will work on all systems, whether AREXX
is present or not.
Commands in config files should not be enclosed in extra quotes like
AREXX programs.
Comment lines may be included in config files by starting the line
with a '#' character.
Note that HamLab 1.x config files cannot be used by HAMLAB PLUS.
COMMAND LIST
ASKFIRST *A
BEEP *A
BITPLANES *SA
CACHE12BIT *A
CACHE24BIT *A
CLEAR
CLEARCONFIG *A
CLOSE
COMPATIBILITY *A
CURVE *
CURVEPOINT *
DISPLAY
DITHER *SA
DITHER2 *SA
EXPORT
FILTERPATH *A
FIXHAM *A
GAMMA *SA
GETATTR
INPUTCROP *S
LOADCONFIG *
LOADCURVES *A
LOADPALETTE *A
LOCKBACKGROUND *SA
LOCKGUI
MESSAGE *
MODULE *A
NOP *
ONESTEP *SA
OPEN
OUTPUTCROP *S
PALETTEMODE *SA
PAN
PIPEDEV *A
QUIT
REQUESTFILE
REQUESTNOTIFY
REQUESTNUMBER
REQUESTRESPONSE
REQUESTSTRING
RESOLUTION *SA
REVERT
REXXCONSOLE *A
SAVE
SAVEAS
SAVECONFIG
SAVECURVES
SAVEMODE *SA
SAVEPALETTE
SCALE *SA
SETCURVE *SA
SETREQ *A
TEMPPATH *A
UNLOCKGUI
WINDOW *A
ASKFIRST *A
Format: ASKFIRST [ON=TRUE=YES | OFF=FALSE=NO]
Template: ON=TRUE=YES/S,OFF=FALSE=NO/S
Purpose: Turns "are you sure" requesters on or off.
Description:
This command controls whether requesters are displayed whenever an
open or clear operation will cause unsaved work to be lost.
Example:
ASKFIRST NO
BEEP *A
Format: BEEP [ON=TRUE=YES | OFF=FALSE=NO]
Template: ON=TRUE=YES/S,OFF=FALSE=NO/S
Purpose: Turns beeping on or off.
Description:
This command controls the "Beep after long functions" setting, which
causes a beep and screen flash after any display, save, or export
function.
Example:
BEEP YES
BITPLANES *SA
Format: BITPLANES [1 | 2 | 3 | 4 | 5 | HALFBRITE | HAM]
Template: 1/S,2/S,3/S,4/S,5/S,HALFBRITE/S,HAM/S
Purpose: Sets the number and type of bitplanes for the output.
Description:
This command sets the number of bitplanes to display and save. Normal
modes allow 1-5 bit planes (1-4 in hires). In addition, the special
HAM and HALFBRITE keywords (available only in lores) select those
special 6 bit plane modes.
Examples:
BITPLANES 4 [4 bit planes]
BITPLANES HAM [HAM mode (implies 6 bit planes)]
CACHE12BIT *A
Format: CACHE12BIT [MEM <memsize>] [DISK <disksize>]
Template: MEM/N/K,DISK/N/K
Purpose: Sets the size(s) of the 12 bit caches.
Description:
This command sets the maximum memory and/or disk size of the 12-bit
cache. The sizes are specified in bytes. You may use "-1" to
indicate a very large cache. (This is quite useful for a RAM cache
since it tells HAMLAB PLUS to use as much RAM as necessary. If that
much RAM is not available, HL+ will automatically switch to a disk
cache, if enabled.) Specifying a zero will disable either a ram or
disk cache.
For the 12-bit cache, 2 bytes are required for each pixel.
If the cache is already in use, the new settings will not take effect
until other changes require the cache to be discarded.
Example:
CACHE12BIT MEM -1 DISK 0 [max memory cache, no disk]
CACHE24BIT *A
Format: CACHE24BIT [MEM <memsize>] [DISK <disksize>]
Template: MEM/N/K,DISK/N/K
Purpose: Sets the size(s) of the 24 bit caches.
Description:
This command sets the maximum memory and/or disk size of the 24-bit
cache. The sizes are specified in bytes. You may use "-1" to
indicate a very large cache. (This is quite useful for a RAM cache
since it tells HAMLAB PLUS to use as much RAM as necessary. If that
much RAM is not available, HL+ will automatically switch to a disk
cache, if enabled.) Specifying a zero will disable either a ram or
disk cache.
For the 24-bit cache, 3 bytes are required for each pixel.
If the cache is already in use, the new settings will not take effect
until other changes require the cache to be discarded.
Example:
CACHE24BIT MEM -1 DISK 10000000 [max mem cache, 10 megs disk]
CLEAR
Format: CLEAR [FORCE]
Template: FORCE/S
Purpose: Clears the current image and all related memory and disk
caches.
Description:
Unloads the current image from memory, and frees any temporary memory
or disk space used by the image.
The FORCE keyword suppresses the confirmation requester.
Examples:
CLEAR [displays requester]
CLEAR FORCE [no requester]
CLEARCONFIG *A
Format: CLEARCONFIG
Template: ,
Purpose: Clears the lists of known input filter and exporter modules.
Description:
This command is used to clear out the list of know input filter and
exporter modules so that a new set can be loaded. The "Save All"
command saves a CLEARCONFIG command at the beginning of a config file.
Example:
CLEARCONFIG
CLOSE
Format: CLOSE [FORCE]
Template: ,
Purpose: Clears the current image and all related memory and disk
caches.
Description:
CLOSE and CLEAR perform exactly the same function.
Examples:
CLOSE [displays requester]
CLOSE FORCE [no requester]
COMPATIBILITY *A
Format: COMPATIBILITY [<mask>]
Template: /N/K
Purpose: Sets internal compatibility switches.
This command allows certain internal settings of HAMLAB PLUS to be
changed. It takes a single argument, which is a 32-bit mask (32
separate binary flags.) The following bits are defined:
Bit Value Meaning
0 1 Write IFF palettes with RGB values like 00, 10, 20, ...
instead of 00, 11, 22, ... ff. The latter method is
correct, but some programs, especially older ones, may
not handle those color values correctly.
1 2 Use Release 2 functions to set pixels in the display
rather than writing to the display directly.
2-31 Reserved for future use. (Do